Add GET /api/v1/bulk-operations/{id}, which returns the bulk operation log
document from the medic-logs database so a caller can poll the progress of
a delete, move or merge it started.

The service only resolves ids carrying the bulk-operation prefix, so the
endpoint cannot be used to read the other log documents that share the
database. Online users only; missing or non-bulk-operation ids return 404.

Add queue(actionOperations) to the bulk-operations service. It builds the log
and action documents and writes the log to medic-logs first, then one action
document per type to medic-sentinel, skipping empty action groups, and returns
the bulk operation id.

Add a medic-sentinel changes-feed listener that queues bulk-operation-action
docs (existing ones on startup, new ones from the feed) and a processor that
works through each in batches, tracking the cursor, then records the result on
the log doc and removes the action doc. Includes the set-contact and
delete-user handlers; the archive handler follows with the archiving work. Adds
the medic-logs handle and getAttachment to sentinel's db.

Add DELETE /api/v1/person/{id} and /api/v1/place/{id} over a shared
delete-contact service that gathers the subtree, its reports (matched by uuid
and shortcode), the primary-contact places to clear, and the linked users, then
queues the bulk operation and returns the breakdown. Gated on
can_delete_contact_hierarchy, with delete_users (requires can_delete_users) and
dry_run query params.

Compute the delete-user operations once (lowering the function's cognitive
complexity) and drop an unreachable empty-subject guard.

Exercise the feed change handler, dedup, the empty-batch guard and a failing
action, use specific assertions, and mark the changes-feed error retry (live
feed infrastructure) as ignored for coverage.

…ld passes

The docs build's JSDoc parser rejected the TypeScript-style optional-property
type on deleteContactHierarchy's @returns; replace it and the record-in-generic
param types with plain JSDoc types.

…anagement-operations' into 10706-delete-contact-hierarchy

The person and place DELETE endpoints delete a hierarchy the same way, so their
controller handlers and @openapi blocks were near-identical. Move the shared
handler into the delete-contact service (the controllers now just point their
delete at it) and pull the delete_users/dry_run params and the response shapes
into shared OpenAPI components referenced from both.

The person and place DELETE endpoints shared one handler and neither checked the
target's type, so a place id sent to the person endpoint would have deleted the
whole place hierarchy. Each endpoint now passes its own type getter to the shared
handler, which rejects an id of the wrong type with a 404, the same way the GET
endpoints already do. The gather-and-queue logic stays type-agnostic in
deleteContactHierarchy.

…n actions

Name the set-contact and delete-user handler functions (they were anonymous
exported arrows), and reduce processAction's cognitive complexity by pulling the
action fetch and the batch loop into helpers.

…narcloud

The poll-to-removal tests depend on the medic#6615 archive handler and were parked
in describe.skip, which trips sonar's "no skipped tests" rule. They land with
that handler instead. Also make the new describe callbacks synchronous.